Accessing metadata with an external host

ABSTRACT

Systems and processes may be used to retrieve metadata from a nonvolatile memory of a portable device and transmit the retrieved metadata to an external host. Metadata may be analyzed using the external host and/or at least a portion of the metadata may be modified based on the analysis. Modified metadata may be transmitted from the external host to a memory controller of the host.

CLAIM OF PRIORITY

This application is a continuation of U.S. application Ser. No. 13/035,314 filed on Feb. 25, 2011, which is a divisional of U.S. application Ser. No. 11/739,818 filed on Apr. 25, 2007, which is incorporated herein by reference.

TECHNICAL FIELD

The present invention relates to systems and processes for accessing data, and more particularly to accessing metadata on a memory of a host using an external host

BACKGROUND

Metadata may describe other data (e.g., user data) stored on memory. Metadata may be stored on the same memory as the user data and provide information about the user data or memory. For example, metadata can provide a variety of information about the memory and its operations, such as data regarding bad blocks on a flash memory or erase counts. Metadata may also provide information such as the time certain data was stored, file size, and/or file type.

SUMMARY

Metadata may be transmitted from a memory of a host to an external host. The metadata may be analyzed and operations may be performed based on the analysis. With the use of portable devices, analyzing and processing the metadata may require relatively large power consumption and processing capabilities and so analyzing and processing may be performed by an external host, such as a computer connected to the portable device.

In one general aspect, metadata for a nonvolatile memory of a portable device is received from the portable device by an external host, an analysis of the retrieved metadata is performed using the external host, the retrieved metadata is modified based on the analysis, and at least the modified portion of the retrieved metadata is transmitted to a memory controller of the portable device. The memory controller controls the memory of the portable device.

Implementations may include one or more of the following features. Received metadata may include time stamps and the time stamps may be analyzed. Analyzing the time stamps may include determining whether data associated with one or more of the time stamps should be rewritten based at least partially on the time stamp. A command signal may be transmitted to rewrite data associated with time stamps, and time stamps associated with rewritten data may be updated. An analysis of time stamps may include determining whether at least one of the time stamps should be adjusted and time stamps may be adjusted based on the determination. Received metadata may include bad block data, where bad block data includes a listing of blocks in the memory that do not satisfy performance criteria. Analysis of bad block data may include transmitting one or more command signals to the memory controller of a host. Command signals may determine whether one or more blocks in the listing of blocks satisfy performance criteria.

Metadata, such as the bad block data, may be modified at least partially based on the analysis. Received metadata may include error correcting code data. An analysis of error correcting code data may include determining whether the error correcting code data should be modified. Modifying the error correcting code may include modifying at least a portion of the error correcting code data. Error correcting code data may be modified to be compatible with the memory controller of the host. Received metadata may include erase count. Analysis of the erase count may include performing testing of blocks based on the erase count. Metadata may be modified at least partially based on the analysis of the erase count. A procedure for moving data among physical blocks may be initiated. A notice may be presented on a user interface. In some implementations, nonvolatile memory may be a flash memory.

In another general aspect, establishment of a connection between an external host and a host is detected, and metadata is retrieved from a memory of the host and transmitted to the external host. An analysis is performed on the retrieved metadata, and the retrieved metadata is modified based on the analysis. At least the modified portion of the retrieved metadata is transmitted for storage on multiple blocks in the memory of the host. Metadata is retrieved across the connection between the host and the external host.

Implementations may include one or more of the following features. Detecting the establishment of a connection may include detecting a bus connection between the external host and the host. Procedures for moving data among physical blocks may be initiated. Retrieved metadata may include time stamps and the time stamps may be analyzed. Analyzing the time stamps may include determining whether data associated with at least one of the time stamps should be rewritten based at least partially on the time stamp. A command signal may be transmitted to rewrite data associated with time stamps, and time stamps associated with rewritten data may be updated. An analysis of time stamps may include determining whether at least one of the time stamps should be adjusted, and times stamps may be adjusted based on the determination.

Retrieved metadata may include bad block data, where bad block data includes a listing of blocks in the memory that do not satisfy performance criteria. Analysis of bad block data may include transmitting one or more command signals to the memory controller of a host. Command signals may determine whether one or more blocks in the listing of blocks satisfy performance criteria. Metadata, such as the bad block data, may be modified at least partially based on the analysis. Retrieved metadata may include error correcting code data. An analysis of error correcting code data may include determining whether the error correcting code data should be modified. Modifying the error correcting code may include modifying at least a portion of the error correcting code data (e.g., making the error correcting code more stringent). Error correcting code data may be modified to be compatible with the memory controller of the memory of the host. Retrieved metadata may include erase count. Analysis of the erase count may include performing testing of blocks based on the erase count. Metadata may be modified at least partially based on the analysis of the erase count.

In another general aspect, a communication interface of an external host communicates with a host to retrieve metadata for the memory of the host. An analysis module of the external host analyzes retrieves metadata and determines whether to modify at least a portion of the retrieved metadata based at least partially on the analysis.

Implementations may include one or more of the following features. The communication interface may include a bus. The communication interface may communicate with the host using one or more network protocols.

The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description, the drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 illustrates an example of a host and an external host.

FIG. 2 illustrates an example configuration of a memory.

FIG. 3 illustrates an example of a memory controller coupled to a memory.

FIG. 4 illustrates an example process of an external host.

FIG. 5 illustrates an example process of analyzing metadata.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 illustrates an example system 100. System 100 may include a host 110. Host 110 may be any electronic or computing device that uses nonvolatile memory including, for example, portable and desktop computers, clients, servers, consumer electronics, calculators, network appliances, media players/recorders, game consoles, mobile phones, email devices, personal digital assistants (PDAs), embedded devices, televisions, system-on-chip (SoC), set-top boxes, audio recorders, handheld data collection scanners, and/or monitoring devices. Host 110 may include a memory 111, a memory controller 112, a processor 113, a presentation interface 114, and/or a communication interface 115. Memory controller 112 and/or processor 113 may include individual chips, a chip set, or can be integrated together on a single chip (e.g., a SoC solution).

Memory 111 may be nonvolatile memory, such as read-only memory (ROM), optical memory (e.g., CD, DVD, or LD), magnetic memory (e.g., hard disk drives, floppy disk drives), NAND flash memory, NOR flash memory, electrically-erasable, programmable read-only memory (EEPROM), Ferroelectric random-access memory (FeRAM), magnetoresistive random-access memory (MRAM), non-volatile random-access memory (NVRAM), non-volatile static random-access memory (nvSRAM), phase-change memory (PRAM), and/or any other memory that does not need its memory contents periodically refreshed and/or can retain information without power. Memory 111 may include memory chips or memory modules (e.g., single in-line memory modules (SIMMs) or dual in-line memory modules (DIMMs)). In some implementations, memory 111 may be electrically erasable. Memory 111 may have a finite number of write/erase cycles. For example, after a number of write/erase cycles, the ability of a cell of memory 111 to maintain a specified charge may be impaired. For example, a memory cell may leak electrons. As another example, an electric charge may not be substantially removable from a memory cell. Cells of a nonvolatile memory may not be individually erasable, such as in flash memory. For example, a cell of a block may be erased by erasing the entire block in which the cell resides. Similarly, writing new data to a portion of a block may require erasing the entire block and rewriting any unchanged portions of the block along with the new data.

In some implementations, memory may be interleaved to increase performance of the host. FIG. 2 depicts a representation of a portion of a memory 200. Memory 200 may include physical blocks 270-277. Each physical block 270-277 may include cells 201-264. For example, physical block 270 may include cells 201-208 and physical block 271 may include cells 209-216. The physical blocks 270-277 and cells 201-264 depicted in FIG. 2 are for purposes of illustration and do not represent a typical implementation. For example, in the case of flash memory, physical blocks typically include a much larger number of cells (e.g., sufficient to store 512 or 2048 bytes), which may be divided into pages (e.g., of 64 bytes), although any size of physical blocks and any number of cells can be used.

During operation, memory 111 may receive signals from memory controller 112 over Input/Output (I/O) bus 116, which enables memory 111 to carry out memory access requests (e.g., read or write operations) received by the memory controller 112 from the processor 113 (see FIG. 1). Memory 111 may be interleaved, so that read or write requests to logical block addresses 280 and 285 (LBAs) are mapped to physical memory addresses that include two or more physical blocks 270-277 (see FIGS. 1 and 2). Interleaving may increase performance (e.g., by decreasing read and/or write times by allowing multiple parallel reads or writes) or protecting against lost data (e.g., by providing some degree of redundancy across different physical blocks) of memory 111. Host 110 (e.g., using processor 113) may perform reads and writes to LBAs 280, 285, which are mapped or translated (e.g., by memory controller 112) to physical block addresses 270-277 of memory. For example, LBA 280 includes cells 202, 210, 218, 226, 234, 242, 250, and 258 and LBA 285 includes cells 204, 214, 220, 228, 236, 247, 252, and 261. In some situations, mapping may help make a memory appear similar to a hard disk drive to the host (e.g., to the operating system of the processor).

In some implementations, physical blocks may be mapped to virtual blocks. Virtual blocks may make a memory appear continuous. For example, bad blocks may be omitted from a virtual block listing. Virtual blocks may be mapped to LBAs to increase memory performance by allowing interleaving.

Memory controller 112 may be any device that manages memory access including, for example, programmable memory controllers, flash disk controllers, direct memory access (DMA) controllers, logic devices, field-programmable gate arrays (FPGAs), and/or central processing units (CPUs). Examples of memory controller 112 may include the family of ATA Flash Disk Controllers (e.g., device nos. SST55LD019A, SST55LD019B, SST55LD019C, etc.), manufactured by Silicon Storage Technology, Inc. (Sunnyvale, Calif.). In some implementations, memory controller 104 supports single-level cell (SLC) and/or multi-level cell (MLC) flash media.

In some implementations, memory controller 112 may recognize control, address, and/or data signals transmitted on bus 117 by processor 113. Memory controller 112 may translate the control, address, and/or data signals into memory access requests on memory 111. Bus 117 may be an Integrated Drive Electronics (IDE)/Advanced Technology Attachment (ATA) bus that transfers control, address and data signals using IDE/ATA standard bus protocol (e.g., ATA-6 bus protocol). IDE/ATA signals may be generated by processor 113 and translated by the memory controller 112 into memory access requests in a format or protocol appropriate for communicating with the memory 111 across bus 116.

Processor 113 may include a programmable logic device, a microprocessor, or any other appropriate device for manipulating information in a logical manner. A processor may execute the operating system for the host. An example of processor 113 is a PP5002 Superintegration™ SoC controller manufactured by PortalPlayer, Inc. (San Jose, Calif.). The PP5002 controller may provide a platform for media player/recorder systems and/or other products that use non-volatile memory.

During use, an application running on processor 113 may request access to data stored on memory 111, see FIG. 1. For example, a user of a host 110 (e.g., a media player/recorder) or an external host 120 (e.g., a desktop or laptop computer) connected to the host 110 may submit a request to save a song to memory 111. A media player/recorder application may send the request to an operating system running on the processor 113, which formats the request into IDE/ATA signals. IDE/ATA signals may be transmitted to memory controller 112 on bus 117 by processor 113. Memory controller 112 may translate the request to access memory 111 via bus 116.

In some implementations, processor 113 may include memory controller 112. For example, the processor 113 and memory controller 112 may be an integrated processor unit. Processors with integrated memory controllers may be commercially available from Freescale Semiconductor (Austin, Tex.) and Texas Instruments (Dallas, Tex.). Utilizing an integrated processor 113 and memory controller 112 may decrease production cost of host 110, facilitate manufacture of host 110, and/or make process execution more efficient. For example, utilizing a single processor/memory controller decreases the number of steps in fabrication.

Presentation interface 114 may present data such as videos, music, messages from the host 105 and/or external host 120, graphical interface for various applications stored on the host (e.g., graphical interface for playing music, videos, manipulating data, etc). For example, presentation interface 114 may present data in visual and/or audio format. Presentation interface 114 may include display device, such as a screen, and/or speakers. Presentation interface may include a graphical interface.

Communication interface 115 may allow communication with other devices. Communication interface 115 may transmit data from host 110 to, and/or receive data from, external host 120 via network protocols (e.g., TCP/IP, Bluetooth, and/or Wi-Fi) and/or a bus (e.g., serial, parallel, USB, and/or FireWire).

FIG. 3 illustrates a portion 300 of a host including a memory 310 and a memory controller 320. Memory 310 may include physical blocks 330 that store data 340 or are capable of storing data. A portion of a physical block 330 may store metadata 350. Metadata may include information about other data in the memory, such as listings of bad blocks in a memory or error correcting codes. Memory 310 may include a first buffer 360 (e.g., a page buffer) that is used to temporarily store data as it is being written to or read from the blocks 330. Memory controller 320 may include or be coupled to a second buffer 370 (e.g., a register or a cache). Second buffer 370 may be a volatile memory such as RAM or a nonvolatile memory such as flash memory.

Memory controller 320 may include a logic device 380 that interprets operations from a host or external host and/or performs operations on a coupled memory. Memory controller 320 operations may include use of at least two buffers 360 and 370 to facilitate operations (e.g., read or write), facilitate random data access operations, and/or increase performance. For example, memory controller 320 may read data from memory 310. In response to a read request from memory controller 320, data from data portion 340 of memory 310 may be loaded into first buffer 360 (e.g., data register or page register). The data in the first buffer 360 may be transmitted to second buffer 370 (e.g., cache, register, or cache register) which is coupled to memory controller 320. The second buffer 370 may accumulate multiple pages of data from the first buffer. Memory controller 320 may reformat data from second buffer 370 for delivery to processor 113 of the host 110 (see FIG. 1) (e.g., in IDE/ATA format). While or after data is transferred from first buffer 360 to second buffer 370, additional data may be loaded from data portions 340 of memory 310 to the first buffer 360.

Memory controller 320 may also input data received from a host or external host into second buffer 370 (e.g., cache) for programming of the array through first buffer 360.

The memory controller 320 may receive requests to read and/or write data to memory 310. The memory controller 320 may format the requests to an instruction format appropriate for the memory 310 (e.g., from or to IDE/ATA format). The memory controller 320 may then transfer the instructions in the appropriate format to the memory 311. The requests in the memory 310 may then be converted to the appropriate electrical charges or the appropriate portions of the memory may be transferred to the second buffer.

Although the above description discusses portions of each block as being for data and/or for metadata, portions of a block that are used for data or metadata may not be fixed. A particular portion of a block may include metadata at some times and include user data or other data at other times.

Host 110 may be coupled to an external host 120, as illustrated in FIG. 1, to transmit and/or receive data. For example, songs and/or videos may be downloaded from external host 120 (e.g., computer) to host 110, which may be a media player or other portable device. As another example, applications, such as firmware, operating systems, software for playing MP3s, software for playing videos and/or upgrades, updates, and/or modifications to applications (e.g., change in available features such as playlists) may be downloaded from external host 120 to host 110. Furthermore, data from the host 110 may be uploaded to external host 120. In addition, host 110 may be coupled to external host 120 to modify data on memory 111 of the host and/or memory 121 of the external host. Host 110 may be coupled to external host 120 to initiate and/or execute processes on the host.

Host 110 may be temporarily coupled to external host. For example, host 110 may be coupled to external host 120 using a connector 125 (e.g., serial bus, parallel bus, USB, and/or FireWire). Connector 125 may be an electrical connector. Connector 125 may allow a removable connection between host 110 and external host 120. A temporary coupling between host 110 and external host 120 may allow the host, such as a portable device, to be disconnected from the external host and/or physically moved away from the external host.

Host 110 may be wirelessly coupled to external host 120. Data may be transmitted using one or more network protocols (e.g., TCP/IP, Wi-Fi, 802.11g, 802.11n, IR or Bluetooth).

External host 120 may be any electronic or computing device including, for example, portable and desktop computers, clients, servers, consumer electronics, network appliances, etc. An external host 120 may include a memory 121, a processor 122, a presentation interface 123, and/or a communication interface 124.

Memory 121 may be a volatile memory (e.g., RAM) and/or nonvolatile memory (disk drive, flash memory, or other suitable memories). Processor 122 may be a programmable logic device, a microprocessor, or any other appropriate device for manipulating information in a logical manner. Presentation interface 123 may present data. Communication interface 124 may allow communication with other devices, such as host 110.

FIG. 4 illustrates an example process 400 of using an external host to manage a memory of a host. An external host may receive metadata from a memory of a host (operation 410). For example, an external host may transmit a request to a host and the host may transmit metadata to the external host in response to the request. A connection between the external host and the host may be detected prior to retrieving metadata from a memory of the host. The external host may be coupled to the host by a connection, such as a USB bus or FireWire bus, and data may be transmitted across the connection. As another example, external host may be indirectly coupled to the host and data may be transmitted using a network protocol.

An analysis of the received metadata may be performed (operation 420). The external host may analyze at least a portion of the metadata to determine if operations should be performed. One or more operations may be performed based on the analysis. For example, the external host may modify at least a portion of the received metadata based on the analysis (operation 430). As another example, the external host may initiate one or more procedures on the host based on the analysis. Metadata may be transmitted from the external host to the host (operation 440). For example, at least metadata that has been modified may be transmitted to a memory of the host.

FIG. 5 illustrates another example process 500 for managing the memory of a host device. A connection between a host and an external host may be detected (operation 505). For example, external host may transmit a command signal (e.g., to determine if the host is ready), and the host may transmit a signal (e.g., indicating a ready condition or that the host is loading connection data) in response to the command signal. The connection may be a bus connection.

The external host may retrieve metadata from a memory of the host using the connection (operation 510). Metadata may include data that describes other data, such as listings of bad blocks in memory (e.g., factory specified bad blocks or other bad blocks), type of error correcting code executed on memory, write and/or erase counts, time stamps for when data is written to memory, and/or data describing mapping between PBAs and LBAs. External host may retrieve at least a portion of the metadata available on a memory of the host. In some implementations, the external host may retrieve specified portions of the metadata. For example, the external host may request time stamp metadata, and the host may transmit the time stamp metadata to the external host. As another example, external host may request and/or retrieve metadata relating to bad blocks, and the host may transmit bad block listings and/or erase counts. As another example, external host may retrieve metadata for a portion of the memory (e.g., for a portion of the PBAs or the LBAs of a memory).

An analysis may be performed on the retrieved metadata (operation 515). A processor of the external host may perform one or more analyses on the retrieved metadata to determine, for example, wear patterns and/or to detect a potential impending failure of the memory. After analysis of metadata, one or more processes may be performed based on the analysis. In some implementations, a processor may include an analysis module that analyzes the metadata (e.g., an application or series of processes).

Bad block listings from retrieved metadata may be analyzed (operation 520). Bad block listings may be analyzed to determine if blocks identified as bad may have been misidentified. Often factory identified bad blocks may be the result of testing over a wide range of temperatures and voltages. While a factory identified bad block may work or appear to work temporarily, the block may fail at other operating conditions and thus factory identified bad blocks may not be analyzed (e.g., retested or scrubbed). Other types of bad blocks may be identified by reading a status register which confirms successful completion of write and/or erase operations of a block. In some implementations, factory identified bad blocks may not be analyzed while a listing of other bad blocks (e.g., identified after the factory identified bad blocks or identified during use of the memory) may be analyzed.

A memory of the host may be tested to determine if bad blocks are appropriately identified (operation 525). For example, an external host may transmit a write and/or an erase command to the memory of the host to determine if a block is bad. External host may initiate testing of previously identified bad blocks on the host.

In some implementations, after testing bad blocks, an error correcting code (ECC) may be changed (operation 530). During programming, a processor and/or memory controller may calculate an ECC based on data. The calculated ECC may then be stored in the memory and associated with the data (e.g., the ECC may be stored in a metadata portion of the memory). When the data is read, the ECC may also be read and a reverse ECC operation may be performed to check that the data is read correctly. The ECC algorithm may correct data errors or a portion of data errors. The number of errors in data that can be corrected by the ECC algorithm may be based on the strength of the algorithm (e.g., a 4-bit ECC, 6-bit ECC, 8-bit ECC). In some implementations, continued use of blocks previously identified as bad or blocks in which errors are occurring may be achieved by increasing the strength of the ECC used. For example, the ECC may be strengthened by utilizing an 8-bit ECC rather than a 4-bit ECC. More stringent forms of ECC may require a larger portion of the memory to store the ECC, thus, the least stringent ECC that satisfies performance criteria (e.g., number of errors allowed) may be used. In some implementations, a more stringent ECC may allow continued use of blocks previously tested as bad or with a high number of errors, and thus, although a larger portion of the memory may be required to store the more stringent ECC, a larger portion of the memory may be available to a user with the continued use of the block, as opposed to if use of the block is discontinued.

In some implementations, bad block listings may be modified based on the testing of the memory (operation 535). For example, bad block listing may be modified if previously identified bad blocks pass testing. Bad block listings may be modified without testing the blocks. For example, at least some of the bad blocks may be removed and/or added to the bad block listing.

Analysis of the retrieved metadata may include analyzing erase counts (operation 540). For example, if erase counts exceed a specified value, the blocks associated with the erase counts may be labeled as a bad block. As another example, erase counts may be analyzed to determine wear patterns.

Some types of electrically erasable memory may have a limited number of write and/or erase cycles. As a block of a memory is erased repeatedly, the block may no longer completely erase (e.g., the tunnel release action in a flash memory may not remove the electrons in the cell). Erase counts may be analyzed to determine bad blocks. For example, when an erase count for a block exceeds a specified value, the block of the memory may be tested to determine if it is a bad block (operation 525). The ECC and/or bad block listings may be modified (operations 530 and 535) based on the testing. Although the above processes are described in terms of erase counts, similar processes may be executed on write counts.

A bad block listing may be modified based on analysis of erase counts (operation 535). For example, if an erase count for a block exceeds a specified value, then the block may be added to the bad block listing. In some implementations, the block may be tested prior to listing the block in the bad block listing. A block may be added to the bad block listing and tested at a later date. A block may be added to the bad block listing when it fails to erase completely as well.

An analysis of the erase count may additionally initiate a procedure for moving data among physical blocks (operation 545). For example, wear leveling procedures may be implemented in response to erase counts exceeding a specified value. Data in a block with a high erase count may be transferred to a block with a lower erase count. Data that will not be changed often may be transferred from a block with a low erase count to a block with a higher erase count.

In some implementations, if blocks are identified as bad after testing or wear leveling procedures are initiated, then mapping metadata (e.g., mapping physical blocks to virtual blocks, mapping physical blocks to LBAs, and/or mapping virtual blocks to LBAs) may be modified. For example, bad blocks and/or blocks with erase counts higher than a specified amount may not be included in the virtual block table. Modifying the virtual block table may affect LBAs, and LBAs may be remapped to virtual blocks. Metadata may be modified as a result, including the mapping of physical blocks to virtual blocks and/or virtual blocks to logical blocks. As another example, LBA 280 may be reordered if physical block 210 is bad and physical blocks 242 and 258 have high erase counts, see FIG. 2. Data in physical blocks 210, 242, and 258 may be replicated on physical blocks 214, 247, and 261, respectively forming a new LBA 285. Mapping metadata that describes the mapping between physical blocks, virtual blocks, and/or logical blocks may be modified based on the reordering. In some implementations, mapping between the physical blocks and virtual blocks may be modified but mapping between the virtual blocks and LBAs may not be modified. For example, although the physical block in which data is stored is changed, it may appear to the processor that no changes have occurred because the LBA remains unchanged.

In some implementations, time stamps in the retrieved metadata may be analyzed (operation 550). In some electrically erasable memory, such as in flash memory, electrons from within a cell may leach causing a potential for corruption of the value of the cell. In multilevel cells, for example, leaching electrons may cause a voltage across a cell to change from 40% to 25% of the maximum voltage and thus may cause the cell to be read incorrectly. If at least a specified amount of time lapses from a time stamp associated with data, the data may be rewritten on the same physical block, a new physical block, the same LBA, a new LBA, and/or combinations thereof. The external host may initiate a procedure for rewriting data based on the analysis of the time stamps (operation 555).

A time stamp may be analyzed to determine if the data associated with the time stamp should be updated and a procedure for rewriting data may be initiated based on the analysis. For example, if a newer version of the data is available, the data may be automatically updated. If the updated data available is older than the time stamp associated with the version of the data on the host, then the updated data may not be transmitted to the host since the updated data may be a newer or the same version as the data residing on the host.

In some implementations, times stamps may be analyzed to determine if a time stamp should be updated (operation 560). For example, when a device is reset, the date and/or the time on a device may be inaccurately modified and/or reset to a default date and/or time. When data is written to the device after it is reset but prior to the data and/or time being updated, it may be associated with an inaccurate time stamp. Correcting time stamps that are inaccurate may prevent data from being rewritten based on an inaccurate time stamp. Correcting time stamps may also facilitate retrieving data, such as when a user searches data on a memory based on time stamps.

An application on the external host may record, on a memory of the external host, time stamps associated with when data was transferred to the host. The time stamp obtained from the host may be compared to the time stamp recorded by the external host. Deviations larger than a specified amount may be corrected. For example, a music management software application may record when songs are downloaded to a music player. If the music player is reset and data is stored after the reset, the music management software application may correct the time stamps associated with data stored after the reset. If the internal clock of the host deviates from an internal clock of the internal clock of the external host, time stamps may also deviate. Thus, time stamps that deviate greater than a specified value may be modified based on time stamps stored in the external host.

In some implementations, a host with an internal clock may store changes in time settings. The changes in time settings may be retrieved by an external host and analyzed. Changes in time settings exceeding a specified amount may indicate inaccuracies in the internal clock of the host and time stamps after the change in time settings may be corrected to account for the inaccuracy in the internal clock. For example, the host may store the change in the time settings on the internal clock periodically such as every hour. If the change in time settings stored exceeds an hour or exceeds an hour plus a tolerated deviation (e.g., 10 minutes), this may indicate that the internal clock is not tracking time accurately and/or that the device has been reset. The time stamps after the unacceptable change in time settings may be modified based on the stored change in the time setting. For example, if after a one hour, internal clock indicates the time setting is 10 years prior to the last clock reading, the time stamps after the last accurate reading may be modified based on the detected change in time setting (e.g., 10 years may be added to each time stamp).

A notice may be presented on the host (e.g., on the presentation interface of the host) based on the analysis (operation 565). The notice may be presented on an external host coupled to the host (e.g., on the presentation interface of the external host). For example, when the number of bad blocks exceeds a specified value and/or an erase count exceeds a specified value, a notice may be presented that the device will fail soon. The notice may be graphic, text, and/or audio signals.

The retrieved metadata may be modified based on the analysis (operation 570). For example, if the bad block listing is modified, the portion of the metadata that includes bad block listings may be modified. Metadata may also be modified when an error correcting code is modified (e.g., made more stringent). Time stamps may also be modified based on the analysis.

The metadata may be transmitted to the host (operation 575). In some implementations, at least the modified portions of the metadata may be transmitted to the host. The external host may transmit a command to the host to modify metadata. The metadata may be stored on a memory of the host (operation 580). The metadata transmitted to the host may replace metadata previously stored on the host and retrieved by the external host.

Although a user has been described as a human, a user may be a person, a group of people, a person or persons interacting with one or more computers, and/or a computer system, as appropriate.

Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof These various implementations can include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.

These computer programs (also known as programs, software, software applications or code) include machine instructions for a programmable processor, and can be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the term “machine-readable medium” refers to any computer program product, apparatus and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term “machine-readable signal” refers to any signal used to provide machine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer (e.g., host or external host) having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices can be used to interact with a user as well. For example, feedback provided to the user by an output device may be any form of sensory feedback (e.g., visual feedback, auditory feedback, and/or tactile feedback) and/or input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back end component (e.g., as a data server), a middleware component (e.g., an application server), a front end component (e.g., a client computer with a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (“LAN”), a wide area network (“WAN”), and the Internet.

The computing system may include clients and servers. A client and a server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made. For example, a processor of the external host may initiate procedures on the host in response to the analysis. The external host may transmit a command to the processor of the host to change metadata based on the analysis. As another example, the external host may request that procedures be initiated in response to analysis. Among other modifications, the described operations may be performed in a different order than is described and some operations may be added or deleted. For example, erase count and/or time stamps may not be analyzed. Metadata may not be modified based on the analysis. In addition, bad block listings may not be tested. As another example, notices may not be present on the host. Accordingly, other implementations are within the scope of this application.

It is to be understood the implementations are not limited to particular systems or processes described. It is also to be understood that the terminology used herein is for the purpose of describing particular implementations only, and is not intended to be limiting. As used in this specification, the singular forms “a”, “an” and “the” include plural referents unless the content clearly indicates otherwise. Thus, for example, reference to “a processor” includes a combination of two or more processors and reference to “a memory” includes mixtures of different types of memories. 

1-20. (canceled)
 21. A method for managing memory comprising: receiving, by an external host, metadata for data blocks in a nonvolatile memory of a portable device, the metadata identifies initial error correction code (ECC) algorithm configured to correct data errors in the data blocks; determining, by the external host, a bad data block in the nonvolatile memory of the portable device based on the received metadata; modifying the received metadata to assign to the bad data block a subsequent ECC algorithm having a strength greater than the initial ECC algorithm; and transmitting the modified metadata to the portable device, the portable device configured to, in response to the modified metadata, execute the subsequent ECC algorithms to correct one or more errors in the bad data block.
 22. The method of claim 21, further comprising: detecting, by the external host, a temporary connection with the portable device; and in response to the detecting, transmitting, through the temporary connection, a request for the metadata for the data blocks in the nonvolatile memory of the portable device.
 23. The method of claim 22, wherein the temporary connection includes a Universal Serial Bus (USB) connection or a FireWire connection.
 24. The method of claim 21, further comprising transmitting at least one of a write command or an erase command to the nonvolatile memory to verify the bad data block.
 25. The method of claim 21, wherein the bad data block comprises a first bad data block, and the method further comprising determining a second bad data block based on an associated time stamp or erase count exceeds a specified threshold, the metadata identifies the associated time stamp or the erase count.
 26. The method of claim 21, further comprising: transmitting a command signal to rewrite data associated with a time stamp; and updating the time stamp in the received metadata.
 27. The method of claim 21, wherein the nonvolatile memory comprises flash memory.
 28. A computer program product encoded on a tangible, non-transitory storage medium, the product comprising computer readable instructions for causing one or more processors to perform operations comprising: receiving, by an external host, metadata for data blocks in a nonvolatile memory of a portable device, the metadata identifies initial error correction code (ECC) algorithm configured to correct data errors in the data blocks; determining, by the external host, a bad data block in the nonvolatile memory of the portable device based on the received metadata; modifying the received metadata to assign to the bad data block a subsequent ECC algorithm having a strength greater than the initial ECC algorithm; and transmitting the modified metadata to the portable device, the portable device configured to, in response to the modified metadata, execute the subsequent ECC algorithms to correct one or more errors in the bad data block.
 29. The computer program product of claim 28, the instructions further comprising: detecting, by the external host, a temporary connection with the portable device; and in response to the detecting, transmitting, through the temporary connection, a request for the metadata for the data blocks in the nonvolatile memory of the portable device.
 30. The computer program product of claim 29, wherein the temporary connection includes a Universal Serial Bus (USB) connection or a FireWire connection.
 31. The computer program product of claim 28, the instructions further comprising transmitting at least one of a write command or an erase command to the nonvolatile memory to verify the bad data block.
 32. The computer program product of claim 28, wherein the bad data block comprises a first bad data block, and the instructions further comprising determining a second bad data block based on an associated time stamp or erase count exceeds a specified threshold, the metadata identifies the associated time stamp or the erase count.
 33. The computer program product of claim 28, the instructions further comprising: transmitting a command signal to rewrite data associated with a time stamp; and updating the time stamp in the received metadata.
 34. The computer program product of claim 28, wherein the nonvolatile memory comprises flash memory.
 35. A computing device, comprising: one or more processors configured to: receive metadata for data blocks in a nonvolatile memory of a portable device, the metadata identifies initial error correction code (ECC) algorithm configured to correct data errors in the data blocks; determine a bad data block in the nonvolatile memory of the portable device based on the received metadata; modify the received metadata to assign to the bad data block a subsequent ECC algorithm having a strength greater than the initial ECC algorithm; and transmit the modified metadata to the portable device, the portable device configured to, in response to the modified metadata, execute the subsequent ECC algorithms to correct one or more errors in the bad data block.
 36. The computing device of claim 35, the processors further configured to: detect a temporary connection with the portable device; and in response to the detecting, transmit, through the temporary connection, a request for the metadata for the data blocks in the nonvolatile memory of the portable device.
 37. The computing device of claim 36, wherein the temporary connection includes a Universal Serial Bus (USB) connection or a FireWire connection.
 38. The computing device of claim 35, the processors further configured to transmit at least one of a write command or an erase command to the nonvolatile memory to verify the bad data block.
 39. The computing device of claim 35, wherein the bad data block comprises a first bad data block, and the processors further configured to determine a second bad data block based on an associated time stamp or erase count exceeds a specified threshold, the metadata identifies the associated time stamp or the erase count.
 40. The computing device of claim 35, the processors further configured to: transmit a command signal to rewrite data associated with a time stamp; and update the time stamp in the received metadata.
 41. The computing device of claim 35, wherein the nonvolatile memory comprises flash memory. 